Release 10.1A: OpenEdge Getting Started:
Application and Integration Services

Preface

This Preface contains the following sections:

Purpose
Audience
Organization
Typographical conventions
OpenEdge messages

Purpose

This manual is the starting point to learn about OpenEdge® support for service-oriented architectures (SOA). It provides a comprehensive overview of the many OpenEdge product components and features that support application development and deployment in an SOA environment. These products and features include:

The OpenEdge AppServer™
The Open Client Toolkit
The AppServer Internet Adapter
Web Services in OpenEdge
Messaging and ESB in OpenEdge
WebSpeed®

All of these product components and features share one of the following functions:

Comprise part of the OpenEdge Application Server product set, which provides the core support for application and integration services.
Play a unique role within OpenEdge application and integration services to help you develop and deploy applications as part of an SOA.

This overview includes an introduction to services, services-oriented architectures, and distributed computing, a broad overview of the OpenEdge Application Server architecture, and a detailed introduction and architecture for each OpenEdge component and feature to help you decide if and how to use it. It also provides references to further documentation on how to use these components and features for application development, deployment, and administration.

Audience

This manual is for anyone who needs to identify and compare the options for working with application and integration services in OpenEdge. It is also for application developers and administrators who are getting started with developing or deploying AppServer application services and developing AppServer clients, including development and deployment of on-Progress 4GL clients, Web services, and Web service clients; developing WebSpeed application services for access by Web browser clients; and implementing Java™ Message Service (JMS) messaging in 4GL applications using the SonicMQ® JMS backbone.

Organization

Chapter 1 "Application and Integration Services in OpenEdge"

Defines what services and service-oriented architectures mean and provides an overview of distributed application computing in OpenEdge.

Chapter 2 "OpenEdge Application Server Architecture"

Provides an overview of the OpenEdge Application Server architecture and components, focussing on its two core application server components, the AppServer and WebSpeed.

Chapter 3 "AppServer for OpenEdge Applications"

Describes basic AppServer operation and its fundamental features and components.

Chapter 4 "OpenEdge Open Clients"

Provides an overview of the Open Client architecture and the tools for developing Open Clients in OpenEdge, allowing non-Progress 4GL clients to access the AppServer.

Chapter 5 "AppServer Internet Adapter"

Provides an overview of the AppServer Internet Adapter (AIA) and the requirements for using it to allow clients to access the AppServer over the Internet.

Chapter 6 "Web Services in OpenEdge—Architecture and Tools"

Provides an overview of OpenEdge support for Web services, both for developing Web services using the Progress 4GL and for accessing industry Web services using the Progress 4GL.

Chapter 7 "OpenEdge Messaging and ESB"

Provides an overview of OpenEdge support for JMS messaging in the 4GL and support for hosting Web services developed in OpenEdge on the Sonic Enterprise Service Bus (Sonic ESB).

Chapter 8 "WebSpeed"

Describes basic WebSpeed operation and its fundamental features and components.

Typographical conventions

This manual uses the following typographical conventions:

Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
Fixed width	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
Fixed-width italics	Fixed-width italics indicate variables in syntax statements.
Fixed-width bold	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.
Period (.) or colon (:)	All statements except DO, FOR, FUNCTION, PROCEDURE, and REPEAT end with a period. DO, FOR, FUNCTION, PROCEDURE, and REPEAT statements can end with either a period or a colon.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

After displaying a message, OpenEdge proceeds in one of several ways:

Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.
Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

** Unknown table name table. (200)

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.
Choose Help Messages and then type the message number to display a description of a specific OpenEdge message.
In the Progress Procedure Editor, press the HELP key or F1.

On UNIX platforms, use the Progress pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.

To use the pro command to obtain a message description by message number:

Start the Progress Procedure Editor:

install-dir/dlc/bin/pro

Press F3 to access the menu bar, then choose Help Messages.
Type the message number and press ENTER. Details about that message number appear.
Press F4 to close the message, press F3 to access the Progress Procedure Editor menu, and choose File Exit.